System and method of managing, maintaining and reporting endoscope medical devices and using device-related status data

ABSTRACT

A system and a method of managing endoscope data are disclosed. The system receives information corresponding to endoscopes in storage, the endoscopes in usage, the endoscopes undergoing the reprocessing operation, and the endoscopes that are undergoing repair in a facility. The system captures each step in storing, usage, reprocessing, and repairing along with the identification of authorized users performing the steps. The system further captures updates made by the users upon storing, usage, reprocessing, and repairing in real-time and updates the information accordingly. The system reduces manual documentation of recording endoscopes inventory and determines how many endoscopes are currently available for operation, how many endoscopes are lying in storage, and how many endoscopes are undergoing repair or reprocessing or cleaning in real-time. Further, the system provides accountability of technicians on each step to properly document uniform and complete safety protocols.

RELATED APPLICATIONS AND CLAIM FOR PRIORITY

The present application claims priority from U.S. Provisional Patent Application Ser. No. 62/935,314, titled “System and Method of Managing, Maintaining and Reporting Endoscope Medical Devices and Using Device-Related Status Data,” Attorney Docket No. SYMP001USP, filed Nov. 14, 2019, which is incorporated herein by its entirety and referenced thereto.

FIELD OF INVENTION

The present invention generally relates to managing endoscope data. More specifically, the present invention relates to a system and method of managing endoscope data in a facility such as a medical institution. Yet further, the present disclosure pertains to a system and method of managing, maintaining and reporting endoscope medical devices and using device-related status data including real-time status of endoscopes in available inventory, in-use, and undergoing reprocessing or repair operation, with facial recognition and other supporting information technologies.

BACKGROUND OF INVENTION

It is known that endoscopes are used in medical investigations for examining and treating the interior of a bodily canal or hollow organ such as colon, bladder, or stomach. Endoscopes generally extend through an orifice or small surgical incision into the patient's body to provide a treating physician with a view of, or access to internal organs or other portions of interest. Endoscopes eliminate the need to physically expose the internal portion of the patient that is of interest to the physician to allow for inspection of that internal portion and less invasive treatment of the patient.

The endoscopes may include, but not limited to, gastrointestinal endoscopes, auriscopes, bronchoscopes, nasopharyngoscopes, fibroscopes, video-endoscopes, and echoendoscopes. Typically, the endoscopes have an external tube containing a series of inner tubes, which serve various functions. As the endoscopes are exposed to both internal and external bodily fluids and tissues, they need to be washed thoroughly and disinfected or reprocessed before re-use. Reprocessing can include a series of steps such as mechanical cleaning of internal and external surfaces with water and detergent, disinfection by immersion or spraying of the endoscope in a high-level disinfectant, rinsing with sterile or filtered water, and drying with alcohol followed by dry air.

Reprocessing of the endoscopes takes a relatively long time. Further, once the endoscopes are returned after reprocessing, they are kept in a storage room until they are taken up for use. Currently, medical institutions such as hospitals document the reprocessing operation manually. Further, the medical institutions use paper records for documenting storage details of the endoscopes.

Several techniques have been disclosed in the past that tried to digitize the requirements in terms of documentation of the reprocessing operation in order to generate a report on whether all process parameters of reprocessing operation were performed correctly or within the range. An example of managing, scheduling, and tracking in real-time the processing of endoscopy equipment in a single site or across multiple sites is disclosed in a United States patent Publication No. 2009/0055215, entitled “Endoscope Management System” (“the '215 Publication”). The '215 Publication discloses a web-based endoscope management system and method for managing, scheduling, and tracking in real-time the processing of endoscopy equipment in a single site or across multiple sites. The system allows various useful information relating to the managed endoscopy equipment and its processing history (such as equipment status, equipment movement, equipment repair history, cost, and procedural efficiencies, what individuals have processed or come into contact with the equipment) to be tracked and analyzed. The system incorporates a user display and prompts to assist users in following the proper processing and cleaning protocols (preparation, pre-cleaning, automated reprocessing, repair, etc.) for the equipment. The system uses a colour-coded display so that pertinent information can be seen at a glance. This system is used in conjunction with a suitable colour-coded labeling scheme to reduce the possibility that users will process the wrong equipment or improperly store it.

Other technique discloses a method that allows documenting the history of the endoscope in the storage unit. An example of managing the use of an endoscope is disclosed in a U.S. Pat. No. 7,670,283, entitled “Endoscope Information System” (“the '283 Patent”). The '283 Patent discloses a system including a use history-storing unit storing the information about the use history of each of a plurality of endoscopes in association with the scope identification information.

It should be understood that the above-discussed disclosures are limited to documenting either the reprocessing operation or recording usage of the endoscope in the storing unit. However, none of the disclosures disclose documenting the endoscopes that are in the storing unit, the endoscopes that are actually in use, and the endoscopes that are undergoing reprocessing operation to have a real-time status of full endoscope inventory in the medical institution. Further, none of the disclosures disclose capturing user identification at each step for documenting the endoscopes in available inventory, in-use and undergoing the reprocessing operation.

Therefore, there is a need for a system and method of managing endoscope data for providing real-time status of endoscopes in available inventory, in-use, and undergoing the reprocessing operation.

SUMMARY

It is an object of the present invention to provide a system and method for managing endoscope data and that avoids the drawback of known techniques.

In order to achieve the object, the present invention provides a system and a method of managing endoscope data. The system receives data corresponding to the complete or total inventory of endoscopes in a facility such as a medical institution or medical facility or a hospital. Specifically, the system receives the data such as endoscopes stored in an endoscope storage unit, endoscopes that are being used in a procedure room, endoscopes that are undergoing the reprocessing operation, and the endoscopes that are under repair.

In accordance with one technical implementation of the present invention, the system provides an endoscope storage unit for storing the endoscopes. The endoscope storage unit stores the endoscopes that are ready for use. Further, the system presents a procedure unit. The procedure unit is placed in a room where the endoscopes are used to perform endoscopy on a patient. Further, the system encompasses a reprocessor unit. The reprocessor unit indicates a device that serves to clean and disinfect the endoscopes after use. Alternatively, the reprocessor unit indicates a computer system for capturing data in a reprocessing room where the endoscopes are cleaned, disinfected, and sterilized. Additionally, the system includes a repair unit. The repair unit captures data on the repair performed on the endoscopes. Here, the repair unit indicates a device used for repairing the endoscope.

In the current implementation, each of the endoscopes has a unique identification number such as a serial number. Further, the system captures information such as a unique identification of technicians and staff members of a medical institution. The technicians perform endoscopy using the endoscopes and update the status of the endoscopes as they are (being) used. Similarly, a technician performing reprocessing operation updates in the system that reprocessing is being performed on an endoscope. Further, the system gets updated with data corresponding to the number of endoscopes stored in the endoscope storage unit.

The system receives the data from the endoscope storage unit, the procedure unit, the reprocessor unit, and the repair unit along with the details of the technician who updated the data. After receiving data from each of the endoscope storage units, the procedure unit, the reprocessor unit, and the repair unit, the system aggregates, and stores the data in the memory.

The data aggregated helps to determine how many endoscopes are currently available for operation, how many endoscopes are lying in storage, and how many endoscopes are undergoing repair or reprocessing or cleaning in real-time. In other words, the system captures information corresponding to how many endoscopes are in use, where they are located, and/or how many are not in use.

In one technical implementation, the system audits the data or information captured to ensure uniform completion and documentation of safety protocols. This helps to check compliance of the authorized users adhering to predefined protocols in managing endoscope data in the facility. Optionally, the system uses the information for operational efficiency, and infection control to make sure there are sufficient endoscopes in the facility at all times.

In another technical feature of the present invention, the system provides a user device that communicatively connects to the system. The user device may include, but not limited to, a mobile phone, a tablet, a laptop, a desktop computer, and so on. A user uses the user device to access the system to obtain the real-time status of the inventory of the endoscopes. In one implementation, the user uses/operates the user device to view the endoscopes that are ready to use i.e., the endoscopes stored in the endoscope storage unit. Further, the user uses the user device to view the endoscopes that are ready or currently in-use in the procedure room. Further, the user uses the user device to view the endoscopes that are undergoing the reprocessing operation. The user further uses the user device to check out details of the endoscope such as the status of the endoscope. The status may include a step in the reprocessing operation that is last performed on the endoscope. Additionally, the user accesses the status such as the time duration for which the endoscope has been kept in the endoscope storage unit from the system. Additionally, the user checks status such as the location of the endoscope from the system.

It one advantageous feature of the present invention, the system ensures reduction or elimination of the manual documentation. Further, the system provides accountability of technicians at each step to properly document uniform and complete safety protocols. In addition, the system provides alerts or reminders to properly document the steps performed in using the endoscopes.

In another advantageous feature of the present invention, the configuration of the system allows authorized users to update the data corresponding to new endoscopes and make changes to existing endoscopes in the facility such that users can track information or status corresponding to each endoscope present in the facility. The information is used for operational efficiency, infection control, making sure there are sufficient endoscopes in the facility at all times, and so on. Additionally, the information is provided on a real-time basis such that the users may conduct analysis on the endoscopes and update the status of the endoscopes to take required action on the endoscope.

In one aspect, the present invention is implemented in a way that a program for causing a computer to execute the above-described managing endoscope data onto a computer-readable storage medium or non-transitory computer-readable medium, and the computer is made to read the program from the non-transitory computer-readable medium, and to execute the program.

Features and advantages of the subject matter hereof will become more apparent in light of the following detailed description of selected embodiments, as illustrated in the accompanying FIGUREs. As will be realized, the subject matter disclosed is capable of modifications in various respects, all without departing from the scope of the subject matter. Accordingly, the drawings and the description are to be regarded as illustrative in nature.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features and advantages of the present invention will become apparent from the following detailed description, taken in combination with the appended drawings, in which:

FIG. 1 illustrates an environment in which a system for managing endoscope data is implemented, in accordance with one embodiment of the present invention;

FIG. 2 illustrates a diagrammatic representation of the system, in accordance with one embodiment of the present invention;

FIG. 3 illustrates a block diagram of a user device 170 communicatively coupled to the system, in accordance with one embodiment of the invention;

FIGS. 4A-4E illustrate a method of managing endoscope data, in accordance with one embodiment of the invention;

FIG. 5 illustrates an example of a compliance chart 400, in accordance with one embodiment of the present invention;

FIG. 6 illustrates an exemplary interface of available endoscopes displayed on the user device, in accordance with one embodiment of the present invention;

FIG. 7 illustrates an exemplary interface of in-use endoscopes displayed on the user device, in accordance with one embodiment of the present invention;

FIG. 8 illustrates an exemplary interface of endoscopes undergoing reprocessing operation displayed on the user device, in accordance with one embodiment of the present invention;

FIG. 9 illustrates an exemplary graph showing quantifying the performance of each department in infection prevention, in accordance with one embodiment of the present invention;

FIG. 10 illustrates a method of managing endoscope data, in accordance with one embodiment of the invention;

FIG. 11 illustrates a method of authenticating users for endoscopy using facial and/or biometric data, in accordance with one exemplary embodiment of the invention;

FIG. 12 illustrates a method of authenticating users and endoscopes at an endoscopy unit using facial and/or biometric data, in accordance with one exemplary embodiment of the invention; and

FIG. 13 illustrates a method of authenticating users for endoscope reprocessing using voice recognition, in accordance with one exemplary embodiment of the invention.

It will be noted that throughout the appended drawings, like features are identified by like reference numerals.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Before the present features and working principle of a system for managing endoscope data is described, it is to be understood that this invention is not limited to the particular system including an endoscope storage unit, a procedure unit, a reprocessor unit, a repair unit, and a user device as described, since it may vary within the specification indicated. Various features for managing endoscope data might be provided by introducing variations within the components/subcomponents disclosed herein. It is also to be understood that the terminology used in the description is for the purpose of describing the particular versions or embodiments only, and is not intended to limit the scope of the present invention, which will be limited only by the appended claims. The words “comprising,” “having,” “containing,” and “including,” and other forms thereof, are intended to be equivalent in meaning and be open-ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items.

It should be understood that the present invention describes a system and method of managing endoscope data. The system receives data corresponding to endoscopes in storage, the endoscopes in usage, the endoscopes undergoing the reprocessing operation, and the endoscopes that are undergoing repair in a medical institution. The system electronically documents each step in storing, usage, reprocessing, and repairing along with the identification of users performing the steps. The system includes a user device. The user device accesses the system to obtain the real-time status of the endoscopes inventory in the medical institution. Various features and embodiments of the system for managing endoscope data are explained in conjunction with the description of FIGS. 1-13.

The present invention discloses a system for managing endoscope data. FIG. 1 shows an environment 100 in which a system 110 for managing endoscope data is implemented, in accordance with one embodiment of the present invention. Environment 100 includes system 110, endoscope storage unit 140, at least one procedure unit 150, at least one reprocessor unit 155, a repair unit 160, and at least one user device 170. Each of endoscope storage unit 140, at least one procedure unit 150, at least one reprocessor unit 155, repair unit 160, and user device 170 communicatively connects to one another via a network 145.

System 110 includes a server or a database having an application to execute functions for managing endoscope data. In alternative embodiments, system 110 operates as a standalone device or connects (e.g., via network 145) to other systems. A person skilled in the art appreciates system 110 can be implemented in any different computing systems, environments, and/or configurations such as a workstation, an electronic device, a mainframe computer, a laptop, and so on. In a networked deployment, system 110 operates as a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

FIG. 2 is a diagrammatic representation of system 110, in accordance with one embodiment of the present invention. System 110 encompasses processor 112 (e.g., central processing unit (CPU), graphics processing unit (GPU,) or both), main memory 114, and a static memory 116, which communicate with at least one other via a bus 118. System 110 further includes video display unit 120 (e.g., liquid crystal display (LCD) or cathode ray tube (CRT)). System 110 further includes alphanumeric input device (e.g., keyboard) and/or touchscreen 122, user interface (UI) navigation device 124 (e.g., mouse), disk drive unit 126, signal generation device 128 (e.g., speaker), and network interface device 130.

Disk drive unit 126 includes machine-readable medium 132 on which is stored one or more sets of instructions and data structures (e.g., software 134) embodying or utilized by any one or more of the methodologies or functions described herein. It should be understood that the term “machine-readable medium” includes a single medium or multiple medium (e.g., centralized or distributed database, and/or associated caches and servers) that stores one or more sets of instructions. The term “machine-readable medium” also includes any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention, or that is capable of storing, encoding or carrying data structures utilized by or associated with such a set of instructions. The term “machine-readable medium” accordingly includes, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals.

Instructions 134 reside, completely or at least partially, within main memory 114 and/or within processor 112 during execution thereof by system 110, main memory 114, and processor 112 also constituting machine-readable media. Network interface device 130 transmits or receives instructions 134 over network 145 utilizing any one of several well-known transfer protocols. Network 145 includes a wireless network, a wired network, or a combination thereof. Network 145 can be implemented as one of the different types of networks, such as an intranet, local area network (LAN), wide area network (WAN), the internet, and the like. Network 145 implements as a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further network 145 includes a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.

Endoscope storage unit 140 indicates a storage unit or an inventory storing a plurality of endoscopes 142. In one example, endoscope storage unit 140 encompasses sensors to detect presence of the plurality of endoscopes 142. In one example, endoscope storage unit 140 includes a storage rack equipped with sensors, a processor, and a memory to store data corresponding to the plurality of endoscopes 142 stored therein. Further, endoscope storage unit 140 presents a transceiver (not shown) for transmitting and receiving information from system 110. In one preferred embodiment, endoscope storage unit 140 shares information corresponding to each of the plurality of endoscopes 142 with system 110 via network 145. For instance, the information may include, but not limited to, number of endoscopes 142 available or present endoscope storage unit 140, serial numbers of the plurality of endoscopes 142, information corresponding to the manufacturer of the plurality of endoscopes 142, date of manufacturing, date and time at which each of plurality of endoscopes 142 received in endoscope storage unit 140, time since each of plurality of endoscopes 142 received at endoscope storage unit 140, and so on.

At least one procedure unit 150 indicates a computer system placed at a procedure room where endoscope 142 is used for screening, diagnosis, and treatment of gastrointestinal (GI) disease. At least one procedure unit 150 may include, but not limited to, a desktop computer, a tablet, and so on. A medical practitioner or a doctor licensed to perform endoscopy procedure on a patient is authorized to operate at least one procedure unit 150. It should be understood that there could be more than one procedure unit 150 present in the environment. As such, a plurality of procedure units 150 communicatively connects to system 110 via network 145. In order to operate at least one procedure unit 150, each medical practitioner is provided with a unique identification number. The medical practitioner uses endoscopes 142 and provides information such as serial number, observations made during the use of endoscope 142 including contamination, repairs needed, damages detected among others with respect to each of endoscopes 142. After providing the information, at least one procedure unit 150 transmits the information to system 110.

At least one reprocessor unit 155 indicates a machine or device that serves to clean and disinfect the endoscopes after use. In one implementation, at least one reprocessor unit 155 includes a processor (not shown), a memory (not shown), and a transceiver (not shown). At least one reprocessor unit 155 communicatively connects to system 110 via network 145. In another implementation, at least one reprocessor unit 155 includes a computer system such as a desktop computer, a tablet, and so on. In the current implementation, at least one reprocessor unit 155 is used for capturing data in a reprocessing room where endoscopes 142 are cleaned, disinfected, and sterilized. As known, endoscopes 142 are to be reprocessed regularly in order to prevent infections. Typically, the reprocessing of GI endoscopes 142 includes steps such as precleaning, cleaning, rinsing, disinfection, rinsing, drying, and storage. During and after performing each of the steps involved in reprocessing of the endoscopes, the authorized technician uses at least one reprocessor unit 155 to update information corresponding to each stage in which any given endoscope 142 is situated and the type of process being conducted on endoscope 142. In order to update information, each technician is provided with a unique authorization detail. The technician uses at least one reprocessor unit 155 to login and update the information based on the type of process performed on the endoscope, the number of endoscopes sent to the storage, and so on.

For example, consider that the technician is using at least one reprocessor unit 155 to update information about the cleaning of endoscope 142. Here, the technician updates information corresponding to the leak test performed by detaching parts separately. Further, the technician updates information corresponding to the cleaning of the external surface of the endoscope with detergent using soft cloths, sponges, or brushes. Further, the technician updates information corresponding to flushing and brushing all accessible channels to remove debris and other contaminants. After cleaning, the technician rinses with clean water to remove the detergent on the endoscopes. Similarly, the technician updates information corresponding to each step involved in reprocessing the endoscopes.

Repair unit 160 indicates a computer system including, but not limited to, a desktop computer, a tablet, a machine used for capturing data in a repair room where endoscopes 142 are repaired for any damage or defect. A repair technician uses repair unit 160 to update information corresponding to damage on endoscopes 142 and the remedy action taken on parts that have been replaced in endoscopes 142. Further, the technician updates information such as the number of endoscopes 142 present in the repair room.

It should be understood that one or more individuals access endoscope storage unit 140, at least one procedure unit 150, at least one reprocessor unit 155, and repair unit 160. Each of one or more individuals is provided with a unique authentication detail to update the data corresponding to endoscopes 142 in endoscope storage unit 140, at least one procedure unit 150, at least one reprocessor unit 155, and repair unit 160. As such, each of the actions performed i.e., data updated from endoscope storage unit 140, at least one procedure unit 150, at least one reprocessor unit 155, and repair unit 160 gets certified or verified by respective individuals with the unique authentication.

As specified above, each of at least one procedure unit 150, at least one reprocessor unit 155, and repair unit 160 transmits the information to system 110. Upon receiving the information, system 110 integrates the information corresponding to each of the endoscopes. Subsequently, system 110 stores the information in main memory 114.

In accordance with one embodiment of the present invention, at least one user device 170 accesses the data stored and processed by system 110. At least one user device 170 may include, but not limited to, a mobile phone, a laptop, a desktop computer, a tablet, a wristwatch, and other electronic devices.

At least one user device 170 includes at least one processor 172. At least one processor 172 includes one or more commonly known CPUs such as microprocessors or microcontrollers. It should be understood that at least one processor 172 is responsible for implementing specific functions under the control of software including an operating system, and any appropriate applications software.

At least one user device 170 includes memory 174 such as volatile memory (e.g., RAM), non-volatile memory (e.g., disk memory, FLASH memory, EPROMs, etc.), unalterable memory, and/or other types of memory. In one implementation, memory 174 stores data, program instructions. The program instructions control the operation of an operating system and/or one or more applications.

At least one user device 170 includes interface(s) 176. Interface 176 presents wired interfaces and/or wireless interfaces. In one implementation, interface 176 has functionality implemented by one or more computer system interfaces such as those described herein and/or generally known to one having ordinary skill in the art.

At least one user device 170 includes device driver(s) 178. Device driver(s) 178 has functionality similar to at least a portion of functionality implemented by one or more computer system driver devices such as those described herein and/or generally known to one having ordinary skill in the art.

At least one user device 170 includes at least one power source and/or power distribution source 180. At least one power source and/or power distribution source 180 includes at least one mobile power source (e.g., battery) for allowing user device 170 to operate in a wireless and/or mobile environment.

At least one user device 170 includes one or more peripheral devices 182. Peripheral devices 182 may include, but not limited to, a memory card reader, a fingerprint reader, and so on.

At least one user device 170 includes a speech processing module 183. Speech-processing module 183 is capable of functionalities such as speech recognition, and speech-to-text conversion.

At least one user device 170 includes display(s) 184. Display 184 implements using LCD display technology, OLED display technology, and/or other types of conventional display technology.

At least one user device 170 includes one or more user I/O Device(s) 186. One or more user I/O device(s) 186 may include keys, buttons, scroll wheels, cursors, touchscreen sensors, audio command interfaces, magnetic strip reader, optical scanner, etc.

At least one user device 170 includes a motion detection module 188. Motion detection module 188 detects motion or movement of user device 170 and/or detects motion, movement, gestures, and/or other input data from the user. In one example, motion detection module 188 includes one or more motion detection sensors such as, for example, MEMS (Micro Electro Mechanical System) accelerometers, that detect the acceleration and/or other movements of user device 170 as the user moves user device 170.

At least one user device 170 includes Audio/Video device(s) 190. Audio/video device(s) 190 includes components for displaying audio/visual media. For example, Audio/Video device(s) 190 may include cameras, speakers, microphones, media presentation components, wireless transmitter/receiver devices for enabling wireless audio and/or visual communication between user device 170 and system 110 and other remote devices (e.g., radios, telephones, computer systems, etc.).

At least one user device 170 includes a user Identification/Authentication module 192. User identification/authentication module 192 determines and/or authenticates the identity of the current user or owner of the user system.

At least one user device 170 includes an operating mode selection component 194. Operating mode selection component 194 is operable to automatically select an appropriate mode of operation based on various parameters and/or upon detection of specific events or conditions such as, for example, the mobile device's current location; the identity of the current user; user input; system override (e.g., an emergency condition detected); proximity to other devices belonging to same group or association; proximity to specific objects, regions, zones, etc.

At least one user device 170 includes information filtering module(s) 196. Information filtering module(s) 196 automatically and dynamically generates filtered information to be displayed on one or more displays of user device 170 using one or more filter parameters.

At least one user device 170 includes a geolocation module 198. Geolocation module 198 acquires geolocation information from remote sources and uses the acquired geolocation information to determine information relating to a relative and/or absolute position of user device 170.

At least one user device 170 includes software/hardware authentication/validation components 200. Software/hardware authentication/validation components 200 is used for authenticating and/or validating local hardware and/or software components, hardware/software components residing at a remote device, user information and/or identity, etc.

At least one user device 170 includes wireless communication module(s) 202. Wireless communication module 202 communicates with external devices using one or more wireless interfaces/protocols such as, for example, 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (WiMAX), 802.22, Cellular standards such as CDMA, CDMA2000, WCDMA, Radio Frequency (e.g., RFID), Infrared, Near Field Magnetics, etc.

At least one user device 170 includes a scanner/camera 204. Scanner/camera 204 scans identifiers and/or other content from other devices and/or objects.

At least one user device 170 includes an Optical Character Recognition (OCR) Processing Engine 206. OCR Processing Engine 206 performs image processing and optical character recognition of images such as those captured by scanner/camera 204.

At least one user device 170 includes user device app components 210. User device app components 210 performs and/or implements various types of functions, operations, actions, and/or other features. User device app components 210 includes UI Component(s) 212, database Component(s) 214, processing component(s) 216, and other components 218.

As specified above, system 110 facilitates managing endoscope data. As such, system 110 can be implemented in a facility, such as a medical institution, hospital or healthcare facility or medical facility, where endoscopes 142 are used for screening, diagnosis, and treatment of gastrointestinal (GI) disease. In order to manage the endoscope data, at first, system 110 receives information corresponding to the date of manufacture, type of endoscope, date of purchase, unique serial number for identifying the endoscope, and so on. For instance, system 110 receives the information of the endoscopes existing in the medical facility. Alternatively, when a new piece of endoscopy is acquired by the medical facility, then information corresponding to the date of manufacture, type of endoscope, date of purchase, and unique serial number for identifying the endoscope is added into system 110.

Further, system 110 receives an input or information corresponding to a list of staff members and physicians authorized to operate the endoscope in each of the departments available in the hospital. Additionally, system 110 receives information corresponding to applicable cleaning protocols including validation periods for the endoscope, repair status, warranty or contract coverage, and purchase cost. This is because; some of the endoscopes have requirements on tracking shelf life or idle time between cleaning cycles. Further, system 110 receives input corresponding to asset information i.e., the sequence of steps that need to be performed on the endoscopes to reprocess the endoscope. In order to receive the input, system 110 communicatively connects to endoscope storage unit 140, at least one procedure unit 150, at least one reprocessor unit 155, repair unit 160. After connecting, each endoscope storage unit 140, at least one procedure unit 150, at least one reprocessor unit 155, repair unit 160 updates system 110 with the status of the endoscopes i.e., an activity such as storage, reprocess, repair, or usage of the endoscope. For instance, consider that the endoscope is being used for performing a procedure, then the physician uses procedure unit 150 to update the status of the endoscope e.g., bedside pre-clean completed. Similarly, for each of the endoscopes, the technicians or staff members update status based on whether the endoscopes are in the storage room, or being used in a procedure, or being reprocessed, or sent for repair. Further, the data corresponding to the status of the endoscopes is stored in system 110. System 110 captures each step performed by at least one reprocessor unit 155 along with user identification to properly complete and document the reprocessing of the endoscopes.

In one alternate embodiment, system 110 receives information such as a room assigned to operate using certain endoscopes, or performing repair operation, or time duration required for performing a medical procedure or repairing. The staff member or technician uses the information to deliver the endoscopes at appropriate locations in the medical facility or obtain data corresponding to the location of certain endoscopes in the medical facility.

As specified above, user device 170 accesses the data stored in system 110. A physician, staff member, a doctor, a technician, management personnel working at the facility operates user device 170. User device 170 accesses department-specific asset information to display/view a dynamic, virtual representation of the endoscope storage unit with stored endoscopes available for use. Further, user device 170 views detailed information of the department endoscopes, reprocessing equipment, and ancillary products.

In order to access the data, system 110 prompts the user of user device 170 to register and authenticate him. The user registers himself with system 110 by providing his name, designation, qualification, and so on. Further, the user registers using his biometric data such as fingerprint data, Personal Identification Number (PIN), facial recognition, and so on. In order to authenticate him, the user uses user identification/authentication module 192, and scanner/camera 204. Alternatively, the user uses a web or mobile-based application to provide a username and password to authenticate him. After the user provides his authentication details, system 110 verifies the authentication details stored in main memory 114 and allows the user to access the data of endoscopes.

Now referring to FIGS. 4A to 4E in conjunction with FIGS. 5, 6, 7, 8, and 9, method 300 of managing endoscope data is explained, in accordance with one embodiment of the present invention. Method 300 is presented to explain documentation of a sequence of steps involved in storing, using, reprocessing the endoscopes. The order in which method 300 of managing endoscope data is described should not be construed as a limitation, and any number of the described method blocks can be combined in any order to implement method 300 or alternate methods.

Additionally, individual blocks may be deleted from method 300 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, method 300 might be implemented using the above-described system 110.

Method 300 including a sequence of steps is performed for managing the endoscope data with the help of system 110, endoscope storage unit 140, at least one procedure unit 150, at least one reprocessor unit 155, repair unit 160, and user device 170.

At step 301, system 110 receives information corresponding to the endoscopes as input. The information includes endoscope asset information such as manufacturer, model number, serial number, and other information of all of the endoscopes. Other information may include high-level disinfection (HLD) endoscopes, test strips, enzymatic detergents, etc. In addition, the information includes the names of departmental staff and/or their identification numbers. Further, system 110 receives information such as names of physician staff, information corresponding to endoscope reprocessor asset information such as manufacturer, model number, serial number, and other information. System 110 stores the information received in main memory 114.

At step 302, user device 170 accesses information of an endoscope. In order to access the information, user device 170 prompts the user to select one of the endoscopes either by entering the name of the manufacturer or the serial number of the endoscope. After selecting, user device 170 retrieves the details from system 110 and displays an option to view details of the endoscopes, as shown in step 304. The details may include endoscope asset information such as the manufacturer of the endoscope, the model number of the endoscope, the serial number of the endoscope, etc. User device 170 prompts the user to view analytics i.e., reports (step 306) and metrics (step 308) corresponding to the endoscope.

In one example, the user operates user device 170 and requests the system 110 to provide details of the “available” endoscopes. Subsequently, system 110 retrieves the data from main memory 114 and displays the data on user device 170. FIG. 6 shows exemplary interface 500 of available endoscopes displayed on user device 170. As can be seen, interface 500 shows a plurality of endoscopes under “available” tab 502 in storage unit 140 for use. The user selects to view the details of the endoscopes based on the manufacturer, model number, serial number, and so on. The details of the available endoscopes get displayed in a plurality of sections. For example, consider the user selects section 510 based on the model number of the endoscope. For the model number selected, user device 170 displays the number of endoscopes of the specific model number available in first subsection 512, model number in second subsection 514, time since the endoscope is present in storage unit 140 in a third subsection, and an image 518 of the endoscope in a fourth subsection.

At step 304, if the user of user device 170 finds a problem i.e. if the user observes any discrepancy or fault or damage in the endoscopes, then the user selects an option to send the endoscope for repair, as shown in step 310. In order to send the endoscope for repair, user device 170 prompts the user to enter his login credentials such as username and personal identification number (PIN), as shown in step 312. Upon providing the PIN, user device 170 prompts the user to enter the problem description for the endoscope, as shown in step 314. At step 316, the user selects an option to send the endoscope for repair. In other words, the user selects a required action to be taken for the endoscope. For the above example, the required action for the damaged endoscope may include sending the endoscope for repair. When the endoscope reaches repair unit 160, a technician performs the repair based on the problem description and updates the nature of repair performed to rectify the problem. System 110 receives the data corresponding to the repair performed on the endoscope and stores the data in main memory 114. After performing the repair, the technician updates system 110 that the endoscope will be sent to endoscope storage unit 140 thereby making the endoscope available for use. Accordingly, the total number of endoscopes available for use or stored in inventory i.e., endoscope storage unit 140 gets updated in system 110.

In one embodiment, at step 320, user device 170 prompts the user to check out more information on the endoscope. Here, the user is a physician who wishes to use the endoscope. The user uses procedure unit 150 to check out more information on the endoscope. In order to check out information, user device 170 prompts the user to enter his login credentials such as username and personal identification number (PIN), as shown in step 322. Upon providing the PIN, user device 170 prompts the user to enter the patient ID. Further, user device 170 prompts the user to select the physician, procedure type, and so on, as shown in step 324. After selecting the physician and procedure type, the endoscope selected is considered as being used in procedure unit 150, as shown in step 326. Subsequently, system 110 gets updated. Subsequently, procedure unit 150 retrieves the details from system 110 and displays an option on user device 170 to view details of the endoscope, as shown in step 336. The details may include endoscope asset information such as the manufacturer of the endoscope, the model number of the endoscope, the serial number of the endoscope, etc.

In one implementation, the user uses user device 170 to request system 110 to display the details of the endoscope that are in-use i.e., the endoscopes that the physicians are using for performing endoscopy. FIG. 7 is exemplary interface 600 showing details of endoscopes under the “in-use”. As can be seen, interface 600 shows a plurality of endoscopes under “in-use” tab 602. “In-use” tab 602 indicates a section displaying the list of endoscopes that are being used in the procedure unit 150. Upon the user selecting the “in-use” tab, the details of the endoscopes that are being used in the procedure room get displayed in a plurality of sections. For example, consider the user selects section 610 to view details of the endoscope being displayed. Based on the selection, user device 170 retrieves the data corresponding to the endoscope selected and displays model number in a first subsection 612, and an image in a second subsection 614.

If at step 304, the user wishes to checkout (step 330) more information on the endoscope, then user device 170 prompts the user to enter his login credentials such as username and personal identification number (PIN), as shown in step 322.

After using the endoscope to perform the endoscopy, the physician enters a description using procedure unit 150 that the “point of use treatment” is completed, as shown in step 334. After entering the description, user device 170 prompts the physician to enter his username and personal identification number (PIN), as shown in step 336. It should be understood that user device 170 prompts the user to enter the PIN to certify and update the description entered by the physician in system 110. After entering the PIN, the physician views the details of the endoscope on user device 170, as shown in step 338. The details may include endoscope asset information such as the manufacturer of the endoscope, the model number of the endoscope, the serial number of the endoscope, etc.

If the physician at step 336 determines that the endoscope needs to be reprocessed, then the endoscope is sent to reprocessing. Subsequently, the physician updates the data in system 110 using procedure unit 150.

Subsequently, the endoscope is sent for reprocessing, as shown in step 340. The technician or staff member conducting the reprocessing operation on the endoscope operates reprocessor unit 155 to update the data in system 110. Upon receiving the endoscope for reprocessing, reprocessor unit 155 prompts the staff member to enter the username and personal identification number (PIN), as shown in step 342. The technician views the details of the endoscope, as shown in step 344. The details may include endoscope asset information such as the manufacturer of the endoscope, the model number of the endoscope, the serial number of the endoscope, etc. After providing the PIN, the technician begins reprocessing of the endoscope, as shown in step 346. Reprocessor unit 155 prompts the technician to enter his PIN, as shown in step 348. As known, endoscopy reprocessing includes a series of steps such as precleaning, leak checking, manual cleaning, rinsing, visual inspection, Minimum Effective Concentration (MEC), High-level disinfection, rinsing, and dry alcohol flush. As such, after completing each of the steps, the technician uses reprocessor unit 155 to update the data to system 110.

For example, after completion of precleaning, the technician uses reprocessor unit 155 to update system 110, as shown in step 350. After step 350, the technician pre-soaks (step 351) the endoscope. Here, the endoscope is pre-soaked for approximately one hour and then sent for a leak check. Further, the technician performs a leak check on the endoscope and updates data that the “leak check is completed” in system 110 using the reprocessor unit 155, as shown in step 352. Further, the technician manually cleans the endoscope and updates data such as “manual cleaning is completed” in system 110 using reprocessor unit 155, as shown in step 352. Further, the technician rinses the endoscope with clean water and updates data such as “rinsing is completed” in system 110 using reprocessor unit 155, as shown in step 356. Subsequently, the technician visually inspects the endoscope and updates data such as “visual inspection is completed” in system 110 using reprocessor unit 155, as shown in step 358. Further, the technician performs the MEC test on the endoscope, as shown in step 362. If the MEC test passes (step 364), then method 300 proceeds to step 368, else, the MEC test is repeated by replacing HLD, as shown at step 366. Here, the reprocess sequence gets aborted and starts a new reprocess sequence.

After completion of the MEC test, method 300 proceeds to step 370, where the technician immerses the endoscope in a high-level disinfectant solution and updates data such as “HLD is completed” in system 110 using reprocessor unit 155. Further, the technician rinses the endoscope with sterile water and updates data such as “rinsing is completed” in system 110 using reprocessor unit 155, as shown in step 372. Subsequently, the technician dries endoscopic channels of the endoscope by flushing with forced air and ethyl or isopropyl alcohol and updates data such as “dry alcohol flush is completed” in system 110 using reprocessor unit 155, as shown in step 374. Subsequently, the technician captures the HLD data and updates system 110, as shown in step 376. After capturing HLD data, the endoscope moves to the available queue (step 378). If steps 350, 351, 352, 354, 356, 358, 368, 370, 372, 374, 376 are not completed, then the technician aborts the cycle at any stage and begins the reprocessing of the endoscope from step 346 until the HLD documentation is complete, as shown in step 376.

In one implementation, the technicians use a compliance chart to follow instructions or guidelines at the time of reprocessing the endoscope. FIG. 5 shows compliance chart 400, in accordance with one exemplary embodiment of the present invention.

After the technician updates the data corresponding to the endoscopes that are undergoing reprocessing, reprocessing unit 155 shares the data with system 110. System 110 stores the data in main memory 114. Subsequently, the user uses user device 170 to access the data corresponding to the endoscopes that are undergoing reprocessing. In order to access the data, the user operates user device 170 to request system 110. Subsequently, system 110 retrieves the data from main memory 114 and shares it with user device 170. FIG. 8 shows exemplary interface 700 of endoscopes undergoing “reprocessing” shown on user device 170. As can be seen, interface 700 shows a plurality of endoscopes under “reprocess” tab 702. The user selects to view the details of the endoscopes based on the manufacturer, model number, serial number, and so on. The details of the endoscopes get displayed in a plurality of sections. For example, consider the user selects a section 710 based on the model number of the endoscope. For the model number selected, user device 170 displays the model number of the endoscope in a first subsection 712, time since the endoscope undergoing “reprocessing” in second subsection 714, and an image of the endoscope in a third subsection 716.

Referring back to FIG. 4E, after completing the HLD documentation, the endoscope gets moved to endoscope storage unit 140 (step 378) indicating that the endoscope is available for use. After moving the endoscope, endoscope storage unit 140 updates the number of endoscopes present in it. Subsequently, endoscope storage unit 140 transmits the data to system 110. System 110 integrates the data received and stores in main memory 114. The user uses user device 170 to access system 110 and obtains the status of the full inventory of endoscopes in the facility i.e., medical institution.

As known, a hospital includes different departments utilizing the endoscopes. In one example, the departments may include an endoscopy department, Gastroenterology department, and internal clinic department. Each of the departments uses endoscope storage unit 140, procedure unit 150, reprocessor unit 155, and repair unit 160. In accordance with the present disclosure, each of endoscope storage unit 140, procedure unit 150, reprocessor unit 155, and repair unit 160 in different departments shares the data corresponding to the endoscopes that are in-use, reprocessing and are available for use in the storage unit with system 110. The data corresponding to the endoscopes in different departments helps to provide quantifiable infection prevention metrics to ensure uniform completion and documentation of safety protocols across all departments in the medical institution.

FIG. 9 shows exemplary graph 800 illustrating the quantifying performance of each department in infection prevention. In the example illustrated, the performance of the endoscopy department, gastroenterology department, and internal clinic department are indicated using first-line 802, a second line 804, and a third line 806, respectively.

Based on the above, it should be understood that system 110 facilitates in managing data i.e., the status of the endoscopes present in the hospital. Specifically, the status of each endoscope is updated from verified physicians with an accurate description such as the endoscope available for use, or endoscope that is being used, or the endoscope undergoing reprocessing, or endoscope sent for repair. The physicians update the status of the endoscopes using endoscope storage unit 140, procedure unit 150, reprocessor unit 155, and repair unit 160 thereby documenting each step involved in storage, usage, and reprocessing of the endoscopes. System 110 receives the data and stores in the main memory 114. The user uses user device 170 to access system 110 and views endoscope inventory, current hand-times, and reprocessing status.

In one embodiment, system 110 generates alerts including reminders to each of endoscope storage unit 140, procedure unit 150, reprocessor unit 155, and repair unit 160 in case system 110 detects an anomaly or discrepancy in complying with protocols that need to be adhered. Alternatively, system 110 generates the alerts upon receiving an update on the status and the information of the endoscope.

Further, system 110 captures each step of the documentation along with the user identification. Thus, system 110 records and recalls the information provided by endoscope storage unit 140, procedure unit 150, reprocessor unit 155, and repair unit 160 at any given point of time. As such, system 110 ensures the accountability of the technician or staff member to properly provide complete data and document the reprocessing of the endoscopes.

It should be understood that the system captures information of endoscopes present in the medical facility. Further, the system captures required action performed by the authorized user on the endoscope e.g., reprocessing or repair of the endoscope. The information can be obtained in real-time and can be used to determine how many endoscopes are currently available for operation, how many endoscopes are lying in storage, how many endoscopes are undergoing repair or reprocessing or cleaning. In other words, the system captures information corresponding to how many endoscopes are in use, where they are located, or how many are not in use.

Further, the system allows authorized users to update data corresponding to new endoscopes and make changes to existing endoscopes in the facility such that users can track information or status corresponding to each endoscope present in the facility. The information can be used for operational efficiency, infection control, making sure there are sufficient endoscopes in the facility at all times, and so on. Additionally, the information is provided on a real-time basis such that the users can conduct analysis on the endoscopes and update the status of the endoscopes to take required action on the endoscope.

FIG. 10 illustrates method 900 of managing endoscope data, in accordance with one embodiment of the present invention. The order in which method 900 of managing endoscope data is described should not be construed as a limitation, and any number of the described method blocks can be combined in any order to implement method 900 or alternate methods. Additionally, individual blocks may be deleted from method 900 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, method 900 is implemented using the above-described system 110.

At first, system 110 receives information corresponding to endoscopes in a facility as shown in step 902. Specifically, processor 112 receives information corresponding to endoscopes. The facility may include, but not limited to, hospital, medical facility, medical institution, endoscope manufacturing unit, and so on. The information includes date of manufacture, type of endoscope, date of purchase, manufacturer, model number, and unique serial number for identifying the endoscope. It should be understood that system 110 receives information corresponding to existing and new endoscopes acquired in the facility.

At step 904, system 110 captures the sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes. Specifically, processor 112 captures the sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes. For example, system 110 captures steps involved in reprocessing of the endoscope for cleaning. In another example, system 110 captures the steps involved in repairing the endoscope. Further, system 110 captures information corresponding to authorized users who are authorized to perform the sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes. In order to capture information corresponding to authorized users, system 110 assigns a unique identification number for technician or medical practitioner who acts as the authorized user to perform the sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes. After providing the information, system 110 stores the information in the main memory 114.

At step 906, system 110 obtains operation information indicative of problem description or required action to be taken on the endoscope while performing a sequence of steps by the authorized user. For instance, when the authorized user i.e., a technician qualified to perform reprocessing operation logs into system 110, the technician enters a description of the cleaning agent used, how the cleaning has been performed. Similarly, if the technician capable of repairing the endoscope logs into system 110, then he performs repair operation and enters the details of the repair performed on the endoscope. After performing required operation, the authorized user enters details of problems found in the endoscope or action taken to rectify the problem such that other users are made aware of the condition of the endoscope when they log into system 110 by providing information of the endoscope.

Additionally, system 110 captures the status of each of the endoscopes. The status indicates the presence of each of the endoscopes undergoing storage, reprocess, repair, or usage of the endoscope. For instance, system 110 captures the status of how many endoscopes are currently available for operation, how many endoscopes are lying in storage, and how many endoscopes are undergoing repair or reprocessing or cleaning. The status corresponding to storing, reprocessing, repairing, or using each of the endoscopes gets captured from endoscope storage unit 140, at least one reprocessor unit 155, repair unit 160, and at least one procedure unit 150, respectively.

Further, system 110 updates the status and information endoscopes accordingly for managing the endoscopes in the facility based on the operation information of the endoscopes, as shown in step 908. For example, if the technician performing reprocessing operation completes the cleaning of the endoscope, he updates the status of the endoscope to move it to endoscope storage unit 140 such that the endoscope is made available in the inventory for later use. Similarly, if the technician performing reprocessing operation identifies an issue in the endoscope, then he sends it to repair unit 160. As such, the number of endoscopes in endoscope storage unit 140 or repair unit 160 gets updated. As the information gets updated in real-time, the users accessing system 110 gets the real-time status of the endoscopes in the facility i.e., how many endoscopes are currently available for operation, how many endoscopes are lying in storage, how many endoscopes are undergoing repair or reprocessing or cleaning.

As the system captures each activity of endoscopes, the information can be used for infection control and better utilization of the endoscopes. For example, if a technician detects an issue i.e., the endoscope was not properly cleaned, then it will be easy for him to identify the endoscope and send the endoscope for cleaning or additional processing. Further, the information can be used to analyze which patients; medical personnel, technicians, and staff might have come in contact with the particular endoscope.

FIG. 11 illustrates process 1000 of authenticating users using their facial features for using/operating endoscopes, in accordance with one exemplary embodiment of the present invention. In the current embodiment, the system comes in a variety of form factors such as a laptop, tablet, desktop, and/or any other electronic device. Here, the facility includes one or more systems in each of the rooms e.g., at the entrance/door where the endoscopes are used to authenticate the users or technicians or physicians operating/using the endoscopes. In order to recognize the users for accessing endoscopes in each specific room, users say first user, second user, etc. register their facial features such as the texture of skin, shape, and size of the nose, lips, eyebrows, the distance between the eyes, depth of eye sockets, shape of cheekbones, hair color, retina scan, etc. After registering, the system stores the users' facial features in the main memory. First user, say technician 1002 approaches system 1004 placed at the entrance of first procedure room. Here, the system includes a scanner/camera configured to recognize the facial features of the first user. In order to recognize first user, system 1004 scans user's face 1006. System 1004 scans facial features 1008 and verifies with facial features stored in the memory. If the facial features match then system 1004 identifies or recognizes 1010 the first user by his name, his designation, and allows him to access system 1004. After identifying first user, system 1004 links all compliance inputs and interactions 1012 of first user with system 1004 ensuring traceability of reprocessing protocols followed by first user 1004.

Second user, say technician 2 1014 approaches system 1016 placed at the entrance of second procedure room. Here, the system includes a scanner/camera configured to recognize the facial features of the user. In order to recognize second user, system 1016 scans user's face 1018. System 1016 scans facial features 1020 and verifies with facial features stored in the memory. If the facial features match then system 1016 identifies or recognizes 1022 second user by his name, his designation, for example, and allows him to access system 1016. Here, the system distinguishes second user from first user using his unique facial features. After identifying second user, system 1016 links all the compliance inputs and interactions 1024 of second user with system 1016 ensuring traceability of reprocessing protocols followed by second user 1016.

Similarly, third user, say clinic director 1026 approaches system 1028 placed at the entrance of third procedure room, say endoscope director's office. Here, the system includes a scanner/camera configured to recognize the facial features of third user. In order to recognize third user 1026, system 1028 scans user's face 1030. System 1028 scans facial features 1032 and verifies with facial features stored in the memory. If the facial features match, then system 1028 identifies or recognizes 1034 the third user by his name, his designation, and allows him to access system 1028. Here, the system distinguishes third user from first user and second user using his unique facial features. After identifying third user, system 1028 links all the compliance inputs and interactions 1036 of the third user with system 1028 ensuring traceability of reprocessing protocols followed by third user 1028.

Similarly, fourth user, say biomed technician 1038 approaches system 1040 placed at the entrance of fourth procedure room, say biomed department. Here, system 1040 includes a scanner/camera configured to recognize the facial features of the user. In order to recognize fourth user, system 1040 scans user's face 1042. System 1040 scans facial features 1044 and verifies with facial features stored. If the facial features match, system 1040 identifies or recognizes 1046 the fourth user by his name, his designation, and allows him to access system 1040. Here, the system distinguishes fourth user from first user, second user, and third user using his unique facial features. After identifying fourth user, system 1040 links all the compliance inputs and interactions 1048 of fourth user with system 1040 ensuring traceability of reprocessing protocols followed by fourth user 1040.

FIG. 12 illustrates process 1100 of authenticating users using biometric and facial features for using/operating endoscopes, in accordance with one exemplary embodiment of the present invention. At first, users say first user 1102 approaches endoscope cabinet 1104 with user device 1108 and picks up or removes endoscope 1106 from endoscope cabinet 1104. System 1110 analyses both first user and endoscope 1106. System 1112 identifies the endoscope that was removed from cabinet 1104. In one example, the system identifies first user using his biometric and/or facial features. Concurrently, system 1114 identifies first user using his facial and/or biometric features. At step 1116, the system distinguishes first user using his facial features and allows him to login and associate his actions performed using the endoscope he removed from cabinet 1104. System 1118 records data associated with first user and endoscope. System 1120 ensures the data recorded is compliant with established protocols and makes the data accessible for other departments.

FIG. 13 illustrates process 1200 of recognizing the voice of users for endoscope reprocessing, in accordance with one exemplary embodiment of the present invention. At first, first user 1202 approaches endoscope cabinet 1204 with user device 1208. Subsequently, first user 1202 picks up or removes endoscope 1206 from endoscope cabinet 1204. First user takes the endoscope to a procedure room. Doctor 1212 performs an endoscopic procedure using the endoscope 1206. After performing the endoscopic procedure, the doctor gives the used endoscope to endoscopic technician 1214 to take it to a reprocessor room. In the scope reprocessing room, a technician performs proper dilution for XXX enzymatic detergent 1216. Here, XXX denotes a variety of variables or numbers. The technician uses system 1220 to obtain information corresponding to the manufacturer-recommended dilution ratio for XXX enzymatic detergent. System 1222 searches the web for the manufacturer's recommended dilution ratio per the IFU for XXX enzymatic solution. System 1224 obtains the manufacturers recommended dilution ratio for XXX enzymatic solution is 3:1 for example per their IFU and announces the data for the technician.

As specified above, the system captures information corresponding to the location of the endoscopes and sequence of steps performed on the endoscopes, duration of time which the endoscopes are in-use or kept idle, or was out for repair or reprocess. Further, the system integrates the information such that the overall inventory can be monitored along with their locations. Whenever there is a shortage of endoscopes, the system alerts users to properly document the steps performed in using or not using the endoscopes.

As each step involved in managing information is digitized and can be obtained in real-time, the system helps to reduce or eliminate the need for manual documentation or record keeping of endoscope data. Further, the system provides accountability of technicians on each step to properly document uniform and complete safety protocols.

The system helps to audit the endoscopes present in the medical institution. For example, the system can be used to check the status of endoscopes on a daily, weekly, monthly basis to obtain information on the number of available scopes, in-use, and so on.

Although the disclosed system is generally described herein as managing endoscope situated at a single medical facility, it should be understood that the disclosed system might be scaled up such that endoscope data of multiple medical facilities can also be managed from a central location.

It should be understood that components shown in figures are provided for illustrative purposes only and should not be construed in a limited sense. A person skilled in the art will appreciate alternate components that might be used to implement the embodiments of the present invention and such implementations will be within the scope of the present invention.

While preferred embodiments have been described above and illustrated in the accompanying drawings, it will be evident to those skilled in the art that modifications may be made without departing from this invention. Such modifications are considered as possible variants comprising the scope of the invention. 

What is claimed is:
 1. A method of managing endoscope data, the method comprising: receiving, by a processor, information corresponding to endoscopes in a facility, wherein the information comprises date of manufacture, type of endoscope, manufacturer, model number, and unique serial number for identifying the endoscope; capturing, by the processor, sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes, wherein the capturing further comprises capturing information corresponding to an authorized user performing the sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes; obtaining, by the processor, operation information indicative of problem description or required action to be taken on the endoscope while performing a sequence of steps by the authorized user; capturing, by the processor, a status indicative of the presence of each of the endoscopes undergoing storage, reprocess, repair, or usage of the endoscope; and updating, by the processor, the status and the information upon storing, reprocessing, repairing, or using each of the endoscopes accordingly for managing the endoscopes in the facility based on the operation information of the endoscopes.
 2. The method of claim 1, wherein the information corresponding to the endoscopes is received from an endoscope storage unit, at least one procedure unit, at least one reprocessor unit, and a repair unit with respect to storage, usage, reprocess, and repair of the endoscopes, respectively.
 3. The method of claim 1, further comprising accessing, by a user device, for obtaining status of the endoscopes undergoing reprocess, storage, repair, or usage of the endoscopes.
 4. The method of claim 3, further comprising authenticating, by the processor, the user device for accessing the status of the endoscopes.
 5. The method of claim 4, further comprising identifying, by the processor, the authorized user performing the sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes.
 6. The method of claim 5, wherein the authorized user is identified using one of facial features and biometric features of the authorized user.
 7. The method of claim 6, further comprising, by the processor, tracing the sequence of steps performed by the authorized user for checking compliance of the authorized user adhering to predefined protocols.
 8. The method of claim 1, wherein the required action to be taken on the endoscope comprises one of sending the endoscope for storage, sending the endoscope for repair, and sending the endoscope for reprocessing.
 9. A system for managing endoscope data, the system comprising: a processor; a memory coupled to the processor, wherein the processor is configured to execute program instructions stored in the memory, to: receive information corresponding to endoscopes in a facility, wherein the information comprises date of manufacture, type of endoscope, manufacturer, model number, and unique serial number for identifying the endoscope; capture sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes; capture information corresponding to an authorized user to perform the sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes; obtain operation information indicative of problem description or required action to be taken on the endoscope while performing a sequence of steps by the authorized user; capture a status indicative of the presence of each of the endoscopes undergoing reprocess, storage, repair, or usage of the endoscope; and update the status and the information upon storing, reprocessing, repairing, or using each of the endoscopes accordingly for managing the endoscopes in the facility based on the operation information of the endoscopes.
 10. The system of claim 9, wherein the processor is configured to receive information corresponding to the endoscopes from an endoscope storage unit, at least one procedure unit, at least one reprocessor unit, and a repair unit with respect to storage, usage, reprocess, and repair of the endoscopes, respectively.
 11. The system of claim 10, wherein the processor is communicatively connected to the endoscope storage unit, the least one procedure unit, the least one reprocessor unit, and the repair unit.
 12. The system of claim 9, further comprises a user device communicatively connected to the system.
 13. The system of claim 12, wherein the user device comprises one of a mobile phone, a tablet, a laptop, a desktop computer, and a smartwatch.
 14. The system of claim 12, wherein the user device accesses the system for obtaining the status of the endoscopes undergoing storage, reprocess, repair, or usage of the endoscopes.
 15. The system of claim 12, wherein the processor is configured to execute the program instructions to authenticate the user device for accessing the status of the endoscopes.
 16. The system of claim 14, wherein the processor is configured to execute the program instructions to generate alerts upon updating the status and the information.
 17. The system of claim 9, wherein the required action to be taken on the endoscope comprises one of sending the endoscope for storage, sending the endoscope for repair, and sending the endoscope for reprocessing.
 18. The system of claim 9, wherein the processor is configured to execute the program instructions to identify the authorized user using one of facial features and biometric features, and wherein the processor traces the sequence of steps performed by the authorized user for checking compliance of the authorized user adhering to predefined protocols.
 19. A non-transitory computer-readable medium embodying a program executable in a computing device for managing endoscope data, the program comprising: a program code for receiving information corresponding to endoscopes in a facility, wherein the information comprises date of manufacture, type of endoscope, manufacturer, model number, and unique serial number for identifying the endoscope; a program code for capturing sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes, wherein the capturing further comprises capturing information corresponding to an authorized user to perform the sequence of steps required for storing, reprocessing, repairing, or using each of the endoscopes; a program code for obtaining operation information indicative of problem description or required action to be taken on the endoscope while performing sequence of steps by the authorized user; a program code for capturing a status indicative of presence of each of the endoscopes undergoing storage, reprocess, repair, or usage of the endoscope; and a program code for updating the status and the information upon storing, reprocessing, repairing, or using each of the endoscopes accordingly for managing the endoscopes in the facility based on the operation information of the endoscopes.
 20. The non-transitory computer-readable medium of claim 19, wherein the required action to be taken on the endoscope comprises one of sending the endoscope for storage, sending the endoscope for repair, and sending the endoscope for reprocessing. 